Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Snyk] Upgrade path-to-regexp from 0.1.7 to 6.2.2 #2

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Upgrade path-to-regexp from 0.1.7 to 6.2.2 #2

wants to merge 1 commit into from

Conversation

YoutacRandS-VA
Copy link
Owner

This PR was automatically created by Snyk using the credentials of a real user.


![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)

Snyk has created this PR to upgrade path-to-regexp from 0.1.7 to 6.2.2.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

⚠️ Warning: This PR contains major version upgrade(s), and may be a breaking change.

  • The recommended version is 45 versions ahead of your current version.

  • The recommended version was released on 2 months ago.

Release notes
Package name: path-to-regexp
  • 6.2.2 - 2024-04-07

    No API changes. Documentation only release.

    Changed

    v6.2.1...v6.2.2

  • 6.2.1 - 2022-05-06

    Fixed

    • Fix invalid matching of :name* parameter (#261) 762bc6b
    • Compare delimiter string over regexp 86baef8

    Added

    v6.2.0...v6.2.1

  • 6.2.0 - 2020-09-29

    Added

    • Support named capturing groups for RegExps (#225)

    Fixed

    • Update strict flag documentation (#227)
    • Ignore test files when bundling (#220)
  • 6.1.0 - 2019-11-20

    Fixed

    • Use /#? as default delimiter to avoid matching on query or fragment parameters
      • If you are matching non-paths (e.g. hostnames), you can adjust delimiter: '.'
  • 6.0.0 - 2019-11-20

    Note: The path syntax has been stabilized with this release, no breaking changes in paths is expected.

    This release reverts the prefix behavior added in v3 back to the behavior seen in v2. For the most part, path matching is backward compatible with v2 with these enhancements:

    1. Support for nested non-capturing groups in regexp, e.g. /(abc(?=d))
    2. Support for custom prefix and suffix groups using /{abc(.*)def}
    3. Tokens in an unexpected position will throw an error
      • Paths like /test(foo previously worked treating ( as a literal character, now it expects ( to be closed and is treated as a group
      • You can escape the character for the previous behavior, e.g. /test\(foo

    Changed

    • Revert using any character as prefix, support prefixes option to configure this (starts as /. which acts like every version since 0.x again)
    • Add support for {} to capture prefix/suffix explicitly, enables custom use-cases like /:attr1{-:attr2}?
  • 5.0.0 - 2019-11-12

    No changes to path rules since 3.x, except support for nested RegEx parts in 4.x.

    Changed

    • Rename RegexpOptions interface to TokensToRegexpOptions
    • Remove normalizePathname from library, document solution in README
    • Encode using identity function as default, not encodeURIComponent
  • 4.0.5 - 2019-11-12

    Removed

    • Remove whitelist in favor of decodeURI (advanced behavior can happen outside path-to-regexp)
  • 4.0.4 - 2019-11-12

    Fixed

    • Remove usage of String.prototype.normalize to continue supporting IE
  • 4.0.3 - 2019-11-12

    Added

    • Add normalize whitelist of characters (defaults to /%.-)
  • 4.0.2 - 2019-11-12
  • 4.0.1 - 2019-11-12
  • 4.0.0 - 2019-11-12
  • 3.2.0 - 2019-11-11
  • 3.1.0 - 2019-08-31
  • 3.0.0 - 2019-01-14
  • 2.4.0 - 2018-08-26
  • 2.3.0 - 2018-08-20
  • 2.2.1 - 2018-04-24
  • 2.2.0 - 2018-03-07
  • 2.1.0 - 2017-10-20
  • 2.0.0 - 2017-08-23
  • 1.8.0 - 2019-11-11
  • 1.7.0 - 2016-11-08
  • 1.6.0 - 2016-10-03
  • 1.5.3 - 2016-06-16
  • 1.5.2 - 2016-06-16
  • 1.5.1 - 2016-06-08
  • 1.5.0 - 2016-05-20
  • 1.4.0 - 2016-05-19
  • 1.3.0 - 2016-05-08
  • 1.2.1 - 2015-08-17
  • 1.2.0 - 2015-05-21
  • 1.1.1 - 2015-05-12
  • 1.1.0 - 2015-05-09
  • 1.0.3 - 2015-01-17
  • 1.0.2 - 2014-12-17
  • 1.0.1 - 2014-08-28
  • 1.0.0 - 2014-08-17
  • 0.2.5 - 2014-08-07
  • 0.2.4 - 2014-08-02
  • 0.2.3 - 2014-07-08
  • 0.2.2 - 2014-07-06
  • 0.2.1 - 2014-06-11
  • 0.2.0 - 2014-06-10
  • 0.1.8 - 2024-04-07

    Added

    v0.1.7...v0.1.8

  • 0.1.7 - 2015-07-28
from path-to-regexp GitHub release notes

Important

  • Warning: This PR contains a major version upgrade, and may be a breaking change.
  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

@snyk-bot
feat: upgrade path-to-regexp from 0.1.7 to 6.2.2
6cbda47 
Snyk has created this PR to upgrade path-to-regexp from 0.1.7 to 6.2.2.

See this package in npm:
path-to-regexp

See this project in Snyk:
https://app.snyk.io/org/youtacrands-va/project/21558e0f-c081-4a9a-b2f1-d385bce788e0?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@YoutacRandS-VA @snyk-bot